Skip to content

deps: Update Build Tools#735

Open
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/build-tools
Open

deps: Update Build Tools#735
renovate-bot wants to merge 1 commit intoGoogleCloudPlatform:mainfrom
renovate-bot:renovate/build-tools

Conversation

@renovate-bot
Copy link
Copy Markdown
Contributor

@renovate-bot renovate-bot commented Jan 28, 2026 •
edited
Loading

This PR contains the following updates:

Package Update Change Age Confidence
cert-manager/cert-manager minor v1.19.2 → v1.20.2 age confidence
github.com/elastic/crd-ref-docs minor v0.2.0 → v0.3.0 age confidence
hashicorp/terraform minor v1.14.3 → v1.15.0 age confidence

Release Notes

cert-manager/cert-manager (cert-manager/cert-manager)

v1.20.2

Compare Source

v1.20.2 fixes invalid YAML generated in the Helm chart when both webhook.config
and webhook.volumes are defined, and bumps Go to 1.26.2 along with dependencies
to address reported vulnerabilities.

Changes by Kind

Bug or Regression
Other (Cleanup or Flake)

v1.20.1

Compare Source

v1.20.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.20.0 adds alpha support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta.

Changes by Kind

Feature
  • Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. (#​8370, @​jcpunk)
  • Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#​8256, @​tareksha)
  • Added support for specifying imagePullSecrets in the startupapicheck-job Helm template to enable pulling images from private registries. (#​8186, @​mathieu-clnk)
  • Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. (#​8355, @​dancmeyers)
  • Added parentRef override annotations on the Certificate resource. (#​8518, @​hjoshi123)
  • Added support for azure private zones for dns01 issuer. (#​8494, @​hjoshi123)
  • Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. (#​7642, @​robertlestak)
  • Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#​7728, @​jcpunk)
  • For Venafi provider, read venafi.cert-manager.io/custom-fields annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. (#​8301, @​k0da)
  • Improve error message when CA issuers are misconfigured to use a clashing secret name (#​8374, @​majiayu000)
  • Introduce a new Ingress annotation acme.cert-manager.io/http01-ingress-ingressclassname to override http01.ingress.ingressClassName field in HTTP-01 challenge solvers. (#​8244, @​lunarwhite)
  • Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#​8195, @​StingRayZA)
  • Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#​8228, @​terinjokes)
  • Added experimental XListenerSets feature gate (#​8394, @​hjoshi123)
Documentation
Bug or Regression
  • Adds logs for cases when acme server returns us a fatal error in the order controller (#​8199, @​Peac36)
  • Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#​8160, @​inteon)
  • Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#​8232, @​eleanor-merry)
  • Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. (#​8456, @​tkna)
  • Fix unregulated retries with the DigitalOcean DNS-01 solver
    Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging (#​8221, @​wallrj-cyberark)
  • Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#​8403, @​calm329)
  • Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#​8424, @​SlashNephy)
  • Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#​8443, @​alviss7)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8173, @​erikgb)
  • Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#​8469, @​SgtCoDFish)
  • Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#​8290, @​octo-sts[bot])
  • When Prometheus monitoring is enabled, the metrics label is now set to the intended value of cert-manager. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). (#​8162, @​LiquidPL)
Other (Cleanup or Flake)

v1.19.5

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This is a simple patch release to fix some reported vulnerabilities. All users are recommended to upgrade.

Changes by Kind

Other (Cleanup or Flake)

v1.19.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.19.4 is a simple patch release to fix some reported vulnerabilities - notably CVE-2026-24051 and CVE-2025-68121. All users should upgrade.

Changes by Kind
Bug or Regression

v1.19.3

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This release contains three bug fixes, including a fix for the MODERATE severity DoS issue in GHSA-gx3x-vq4p-mhhv. All users should upgrade to the latest release.

Changes by Kind

Bug or Regression
  • Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#​8415, @​cert-manager-bot)
  • Fixed an issue where HTTP-01 challenges failed when the Host header contained an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#​8436, @​cert-manager-bot)
  • Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#​8468, @​SgtCoDFish)
Other (Cleanup or Flake)
elastic/crd-ref-docs (github.com/elastic/crd-ref-docs)

v0.3.0

Compare Source

Changelog

hashicorp/terraform (hashicorp/terraform)

v1.15.0

Compare Source

1.15.0 (April 29, 2026)

NEW FEATURES:

  • We now produce builds for Windows ARM64 (#​32719)

  • You can set a deprecated attribute on variable and output blocks to indicate that they are deprecated. This will produce warnings when passing in a value for a deprecated variable or when referencing a deprecated output. (#​38001)

  • backend/s3: Support authentication via aws login (#​37976)

  • validate: The validate command now checks the backend block. This ensures the backend type exists, that all required attributes are present, and that the backend's own validation logic passes. (#​38021)

  • convert function, which allows for precise inline type conversions (#​38160)

  • Terraform now supports variables and locals in module source and version attributes (#​38217)

ENHANCEMENTS:

  • config: output blocks now can have an explicit type constraints (#​36411)

  • ssh-based provisioner (file + remote-exec): Re-enable support for PowerShell (#​37794)

  • terraform init log timestamps include millisecond precision (#​37818)

  • init: skip dependencies declared in development override. This allows you to use terraform init with developer overrides and install dependencies that are not declared in the override file. (#​37884)

  • Terraform Test: Allow functions within mock blocks (#​34672)

  • improve detection of deprecated resource attributes / blocks (#​38077)

  • Deprecation messages providers set on resources / blocks / attributes are now part of the deprecation warning (#​38135)

  • Include which attribute paths are marked as sensitive in list_start JSON logs (#​38197)

  • Add input variable validation for Stacks (#​38240)

  • When comparing a container value to null, only top level marks are now considered for the result. (#​38270)

  • As part of supporting variables in module sources, most commands now accept variable values (#​38276)

BUG FIXES:

  • testing: File-level error diagnostics are now included in JUnit XML skipped test elements, ensuring CI/CD pipelines can detect validation failures (#​37801)

  • A refresh-only plan could result in a non-zero exit code with no changes (#​37406)

  • cli: Fixed crash in terraform show -json when plan contains ephemeral resources with preconditions or postconditions (#​37834)

  • cli: Fixed terraform init -json to properly format all backend configuration messages as JSON instead of plain text (#​37911)

  • state show: The state show command will now explicitly fail and return code 1 when it fails to render the named resources state (#​37933)

  • apply: Terraform will raise an explicit error if a plan file intended for one workspace is applied against another workspace (#​37954)

  • lifecycle: replace_triggered_by now reports an error when given an invalid attribute reference that does not exist in the target resource (#​36740)

  • backend: Fix nil pointer dereference crash during terraform init when the destination backend returns an error (#​38027)

  • stacks: send progress events if the plan fails for better UI integration (#​38039)

  • stacks: component instances should report no-op plan/apply. This solves a UI inconsistency with convergence destroy plans (#​38049)

  • backend/http: Return conflicting lock info from HTTP backend instead of the lock that failed to be taken (#​38144)

  • states: fixed a bug that caused Terraform to be unable to identify when two states had different output values. This may have caused issues in specific circumstances like backend migrations. (#​38181)

  • cloud: terraform cloud and registry discovery network requests are now more resilient, making temporary network or service related errors less common (#​38064)

  • Enable formatting of .tfquery.hcl files by terraform fmt (#​38398)

  • Fix validate not returning JSON for some early diagnostics (#​38400)

  • Fix Terraform Stacks plugin installation error (#​38406)

NOTES:

  • command/init: Provider installation was refactored to enable future enhancements in the area. This results in different order of operations during init and 2 new log messages replacing one (initializing_provider_plugin_message). The change should not have any end-user impact aside from the init command output. (#​38227)

UPGRADE NOTES:

  • backend/s3: The AWS_USE_FIPS_ENDPOINT and AWS_USE_DUALSTACK_ENDPOINT environment variables now only respect true or false values, aligning with the AWS SDK for Go. This replaces the previous behavior which treated any non-empty value as true. (#​37601)

Previous Releases

For information on prior major and minor releases, refer to their changelogs:

v1.14.9

Compare Source

1.14.9 (April 20, 2026)

BUG FIXES:

  • Fix Terraform Stacks plugin installation error (#​38406)

v1.14.8

Compare Source

1.14.8 (March 25, 2026)

BUG FIXES:

  • Prevent crash in the display of relevant attributes after provider upgrades (#​38264)

v1.14.7

Compare Source

1.14.7 (March 11, 2026)

NOTES:

  • Bump Go version to 1.25.8 to suppress security scanner false positives (#​38249)

v1.14.6

Compare Source

1.14.6 (February 25, 2026)

BUG FIXES:

  • terraform test: return error when provider config is invalid (#​38084)

v1.14.5

Compare Source

1.14.5 (February 11, 2026)

BUG FIXES:

  • Fixed an issue where terraform stacks validate was failing to resolve relative paths for modules (#​38025)

v1.14.4

Compare Source

1.14.4 (January 28, 2026)

BUG FIXES:

  • backend: Fix nil pointer dereference crash during terraform init when the destination backend returns an error (#​38027)

  • Fixes an issue where any warning diagnostics generated during terraform query execution failed to render in the cloud backend session (#​38040)

  • actions in modules without instances failed the plan graph (#​38089)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested a review from a team as a code owner January 28, 2026 12:30
@renovate-bot renovate-bot changed the title deps: Update dependency hashicorp/terraform to v1.14.4 deps: Update Build Tools Feb 2, 2026
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch 2 times, most recently from 7ed7c42 to cb3803c Compare February 25, 2026 18:47
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch 2 times, most recently from d5a09ab to 0aaf5de Compare March 11, 2026 17:02
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch 2 times, most recently from e1b295f to d8e3571 Compare March 27, 2026 19:53
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch from d8e3571 to e8859ab Compare April 11, 2026 18:50
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch from e8859ab to 9fe0f21 Compare April 21, 2026 00:27
@renovate-bot renovate-bot force-pushed the renovate/build-tools branch from 9fe0f21 to b001730 Compare April 29, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@hessjcg hessjcg

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@renovate-bot @hessjcg